Integrated firewall, ips, and virus scanner system and method

ABSTRACT

A system, method and computer program product are provided including a router and a security sub-system coupled to the router. Such security sub-system includes a plurality of virtual firewalls, a plurality of virtual intrusion prevention systems (IPSs), and a plurality of virtual virus scanners. Further, each of the virtual firewalls, IPSs, and virus scanners is assigned to at least one of a plurality of user and is configured in a user-specific.

RELATED APPLICATIONS

The present application is a continuation of application Ser. No.11/033,426 filed on Jan. 10, 2005, which is incorporated herein byreference.

FIELD OF THE INVENTION

The present invention relates to computer and network security, and moreparticularly to related security services.

BACKGROUND

In the space of just over a decade, the Internet, because it providesaccess to information, and the ability to publish information, inrevolutionary ways, has emerged from relative obscurity to internationalprominence. Whereas, in general, an internet is a network of networks,the Internet is a global collection of interconnected local, mid-level,and wide-area networks that use the Internet Protocol UP) as the networklayer protocol. Whereas the Internet embraces many local- and wide-areanetworks, a given local- or wide-area network may or may not form partof the Internet.

As the Internet and its underlying technologies have become increasinglyfamiliar, attention has become focused on Internet security and computernetwork security in general. With unprecedented access to informationhas also come unprecedented opportunities to gain unauthorized access todata, change data, destroy data, make unauthorized use of computerresources, interfere with the intended use of computer resources, etc.These opportunities have been exploited time and time again by manytypes of malware including, but is not limited to computer viruses,worms, Trojan horses, etc. As experience has shown, the frontier ofcyberspace has its share of scofflaws, resulting in increased efforts toprotect the data, resources, and reputations of those embracingintranets and the Internet.

To combat the potential risks associated with network usage, numeroussecurity tools have been developed such as firewalls, intrusionprevention systems (IPSs), virus scanners, etc. To date, however, suchtools are typically packaged for either individual or enterprise use. Inthe context of enterprise use, the foregoing tools are typicallypackaged for employment by large corporations, without the ability totailor and/or select security policies on a group-by-group/user-by-userbasis.

There is thus a need for overcoming these and/or other problemsassociated with the prior art.

SUMMARY

A system, method and computer program product are provided including arouter and a security sub-system coupled to the router. Such securitysub-system includes a plurality of virtual firewalls, a plurality ofvirtual intrusion prevention systems (IPSs), and a plurality of virtualvirus scanners. Further, each of the virtual firewalls. IPSs, and virusscanners is assigned to at least one of a plurality of users and isconfigured in a user-specific manner.

In one embodiment, the security sub-system may further include aplurality of anti-spam modules, content filtering modules, uniformresource locator (URL) filtering modules, virtual private network (VPN)modules, spyware filtering modules, adware filtering modules, etc.Further, each of such modules may be assigned to at least one of theplurality of the users, and may be configured in the user-specificmanner.

As a further option, the user-specific configuration may be providedutilizing a plurality of user-specific policies. Still yet, theuser-specific policies may be selected by each user. Even still, theuser-specific policies may be selected utilizing a graphical userinterface. Such graphical user interface may include a virtual firewallinterface, a virtual IPS interface, a virtual virus scanner interface,etc.

In yet another embodiment, the security sub-system may reside in frontof the router, in hack of the router, and/or even take the form of acomponent of the router.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network architecture, in accordance with oneembodiment.

FIG. 2 shows a representative hardware environment that may beassociated with the data server computers and/or end user computers ofFIG. 1, in accordance with one embodiment.

FIG. 3 illustrates a system with two exemplary service providerdeployments, in accordance with one embodiment.

FIG. 4 shows a system that illustrates where network security servicesmay be deployed from a functional level, in accordance with oneembodiment.

FIG. 5 illustrates a system involving one possible on-the-wiredeployment model, in accordance with one embodiment.

FIG. 6 illustrates a system involving an example of a deployment for asmaller point-of-service (POP), in accordance with one embodiment.

FIG. 7 illustrates a system involving another example of a deploymentfor a larger point-of-service (POP), in accordance with one embodiment.

FIG. 8 illustrates one possible graphical user interface capable ofbeing used for policy management, in accordance with one embodiment.

FIG. 9 illustrates possible graphical user interface capable of beingused for firewall policy management, in accordance with one embodiment.

FIG. 10 illustrates one possible graphical user interface for policymanagement, in accordance with one embodiment.

FIG. 11 illustrates one possible graphical user interface for providingdetails on applied policies, in accordance with one embodiment.

FIGS. 12-13 illustrate possible graphical user interfaces for providingcontent/uniform resource locator (URL) filtering, in accordance with oneembodiment.

FIG. 14 illustrates a system for implementing service providermanagement hooks, in accordance with one embodiment.

FIGS. 15-16 illustrate systems for providing an optional failoverfeature.

DETAILED DESCRIPTION

FIG. 1 illustrates a network architecture 100, in accordance with oneembodiment. As shown, a plurality of networks 102 is provided. In thecontext of the present network architecture 100, the networks 102 mayeach take any form including, but not limited to a local area network(LAN), a wide area network (WAN) such as the Internet, etc.

Coupled to the networks 102 are data server computers 104 which arecapable of communicating over the networks 102. Also coupled to thenetworks 102 and the data server computers 104 is a plurality of enduser computers 106. In the context of the present description, such enduser computers 106 may take the form of desktop computers, laptopcomputers, hand-held computers, cellular phones, personal dataassistants (PDA's), and/or any other computing device.

In order to facilitate communication among the networks 102, at leastone router 108 (which may take the form of any type of switch, in thecontext of the present description) is coupled therebetween. In use,such router 108 has a security system (i.e. sub-system, etc.) coupledthereto.

Such security system includes a plurality of virtual firewalls, aplurality of virtual intrusion prevention systems (IPSs), and aplurality of virtual virus scanners. Further, each of the virtualfirewalls, IPSs, and virus scanners is assigned to at least one of aplurality of users and is configured in a user-specific manner.

Of course, such security system modules may be expanded in any desired,optional way. For example, the security system may further include aplurality of anti-spam modules, content filtering modules, uniformresource locator (URL) filtering modules, virtual private network (VPN)modules, spyware filtering modules, Aware filtering modules, etc. Stillyet, each of such modules may be assigned to at least one of theplurality of the users and may be configured in the user-specificmanner.

More information regarding optional functionality and architecturalfeatures will now be set forth for illustrative purposes. It should benoted that such various optional features each may (or may not beincorporated with the foregoing technology of FIG. 1, per the desires ofthe user.

Performance of anti-virus scanning (especially scanning of files) isquite slow. When one adds the possibility of files being compressed,scanning of files becomes much slower. Various embodiments may,optionally, improve anti-virus scanning performance by keeping a MAC forfiles it already has scanned. When files that have been scanned traversethe network, the system may calculate the MAC and use it to determine ifthe file has to be scanned.

FIG. 2 shows a representative hardware environment that may beassociated with the data server computers 104 and/or end user computers106 of FIG. 1, in accordance with one embodiment. Such figureillustrates as typical hardware configuration of a workstation inaccordance with one embodiment having a central processing unit 210,such as a microprocessor, and a number of other units interconnected viaa system bus 212.

The workstation shown in FIG. 2 includes a Random Access Memory (RAM)214, Read Only Memory (ROM 216, an I/O adapter 218 for connectingperipheral devices such as disk storage units 220 to the bus 212, a userinterface adapter 222 for connecting a keyboard 224, a mouse 226, aspeaker 228, a microphone 232, and/or other user interface devices suchas a touch screen not shown) to the bus 212 communication adapter 234tier connecting the workstation to a communication network 235 (e.g., adata processing network) and a display adapter 236 for connecting thebus 212 to a display device 238.

The workstation may have resident thereon any desired operating system.It will be appreciated that an embodiment may also be implemented onplatforms and operating systems other than those mentioned. Oneembodiment may be written using JAVA, C, and/or C++ language, or otherprogramming languages, along, with an object oriented programmingmethodology. Object oriented programming (OOP) has become increasinglyused to develop complex applications.

Our course, the various embodiments set forth herein may be implementedutilizing hardware, software, or any desired combination thereof. Forthat matter, any type of logic may be utilized which is capable ofimplementing the various functionality set forth herein.

FIG. 3 illustrates a system 300 with two exemplary service providerdeployments, in accordance with one embodiment. As an option, thepresent system 300 may be implemented in the context of the architectureand environment of FIGS. 1 and/or 2. Of course, however, the system 300may be carried out in any desired environment.

In one embodiment 302, the system 300 provides functionality outside a“cage aggregation” in a hosting environment. In another embodiment 304,the system 300 provides “on-the-wire” security services (delivered by aservice provider via equipment at an edge of a network).

FIG. 4 shows a system 400 that illustrates where network (i.e. serviceprovider “edge,” etc.) security services may be deployed from afunctional level, in accordance with one embodiment. As an option, thepresent system 400 may be implemented in the context of the architectureand environment of FIGS. 1 and/or 2. Of course, however, the system 400may be carried out in any desired environment.

As shown in scenarios 1)-7), the security services may be used toprotect corporate customers in 7 different deployments/locations, asdescribed. For example, the security services may be positioned onleased private lines from a main office (MO) to a partner, jointventure, etc. office. See 1). Further, the security services may bepositioned on leased private, lines from a main office to a back office(BO) or remote office (RO). See 2). Still yet, the security services maybe positioned on Internet lines from a main office to a back office orremote office. See 3).

In a further embodiment, the security services may be positioned onInternet lines from a main office to a small office/home office (SOHO).See 4). Even still, the security services may be positioned on Internetlines from a main office to a back office such as a location offshore(i.e. India, etc.). See 5). Further, the security services may bepositioned on Internet lines from a main office to a partner, jointventure, etc. office. See 6). Finally, the security services may bepositioned on Internet lines to a main office. See 7).

FIG. 5 illustrates a system 500 involving one possible on-the-wiredeployment model, in accordance with one embodiment. As an option, thepresent system 500 may be implemented in the context of the architectureand environment of FIGS. 1 and/or 2. Of course, however, the system 500may be carried out in any desired environment.

With reference to FIG. 5, a mid-size business main office 502 and branchoffice 504 are possible locations for the aforementioned securityservices provided by a service provider, it should be noted that, inthis model, it may be assumed that an aggregate router 506 resides infront and adds virtual local area network (VLAN) tags.

In various embodiments, the aforementioned VLAN tags may be stripped bythe security services and/or router. Further, static routing, or evenopen-shortest-path-first (OSPF) techniques, may be used. Also, supportmay be provided for both a transparent and routing mode. This may evenbe implemented on a per-port basis to allow configuration for customersof a service provider.

The present embodiment may further act as a Dynamic Host ConfigurationProtocol (DHCP) server for an internal network with the followingparameters of Table 1 configurable by the user and/or per domain.

TABLE 1 Range of IP Addresses To Assign Network Mask To Assign RenewalTime (in seconds): This specifies how often the clients have to get anew DHCP address Optional (user could just leave blank): Domain ToAssign Optional (user could just leave blank): IP addresses of DNSServers To Assign Optional (user could just leave blank): Any staticroutes to assign Optional (user could just leave blank): WindowsInternet Name Service (WINS) Server IP addresses

As an option, the present embodiment may further support IPv6.

FIG. 6 illustrates a system 600 involving an example of a deployment fora smaller point-of-service (POP), in accordance with one embodiment. Asan option, the present system 600 may be implemented in the context ofthe architecture and environment of FIGS. 1 and/or 2. Of course,however, the system 600 may be carried out in any desired environment.As shown, the current system 600 aggregates very low bandwidth linesfrom small business environments 602, and small office/home officeenvironments 604.

FIG. 7 illustrates a system 700 involving another example of adeployment for a smaller point-of-service (POP), in accordance with oneembodiment. As an option, the present system 700 may be implemented inthe context of the architecture and environment of FIGS. 1 and/or 2. Ofcourse, however, the system 700 may be carried out in any desiredenvironment. The present deployment may be possible with use of OCXPacket-over-SONET I/O cards. Of course, any desired type of deploymentis possible.

FIG. 8 illustrates one possible graphical user interface 800 capable ofbeing used for policy management, in accordance with one embodiment. Asan option, the present graphical user interface 800 may be implementedin the context of the architecture and environment of FIGS. 1 and/or 2.Of course, however, the graphical user interface 800 may be carried outin any desired environment.

In use, policies may be created for the various aforementioned securityfunctions and may be set (and provisioned in a service provider and/orenterprise embodiment, for example) for specific domains, customers,etc. It may be noted that the graphical user interface 800 (and relateduser interfaces to be set forth hereinafter) are merely illustrative,and should not be considered limiting in any manner.

Using a “Policies” tab 802, various policies may be created. Dependingon what types of functionality (i.e. firewalls, IPSs, virus scanners,etc.) are enabled, the related headings 804 may be optionally “grayedout” to indicate that the functionality is either not activated by aparticular user or not subscribed to the user.

By selecting the different headings 804, a user may select/edit policiesto control the different security functionality. For example, as shownin FIG. 8, options 806 such as adding, cloning, viewing/editing, anddeleting policies are provided. Further, a table 808 may be provided fordisplaying policy names, identifying a source of each policy, displayingan inbound rule set, displaying an outbound rule set, displaying aneditable function, etc.

In the context of a firewall policy editor interface, there may be aplurality of sections, including sections for creating different typesof policies and at least one section for creating firewall objects (i.e.network objects, service objects and time objects, etc.).

FIG. 9 illustrates one possible graphical user interface 900 capable ofbeing used for firewall policy management, in accordance with oneembodiment. As art option, the present graphical user interface 900 maybe implemented in the context of the architecture and environment ofFIGS. 1 and/or 2. Of course, however, the graphical user interface 909may be carried, out in any desired environment.

Similar to the interface of FIG. 8, options 902 such as adding, cloning,viewing/editing, and deleting policies are provided, Further, a table904 may be provided for displaying policy names, identifying a source ofeach policy, displaying an editable function, etc.

For a specific function configuration to appear in the various userinterfaces, it may, in one embodiment, be required to be provisioned bya reseller or the like. For example, a reseller may only want intrusionprevention system (IPS) services to be provisioned to 2 of 4 subscribers(who signed up and paid for such service), This provisioning of servicesand constraints may be carried out utilizing a reseller user interface,separate from the subscriber user interface.

As an option, a provisioning section of a user interface may bedisplayed only if a higher-level domain (i.e. higher in a hierarchicaltree, etc.) has enabled an “allow child provisioning” option. In otherwords, the aforementioned provisioning section may only be displayed ina specific domain if the original function is activated, and thefunction is provisioned to the domain (and, of course, the “allow childprovisioning” option is selected).

FIG. 10 illustrates one possible graphical user interface 1000 forpolicy management, in accordance with one embodiment. As an option, thepresent graphical user interface 1000 may be implemented in the contextof the architecture and environment of FIGS. 1 and/or 2. Of course,however, the graphical user interface 1000 may be carried out in anydesired environment.

As shown, a default policy that is to be provisioned may be chosen via apull-down menu 1002 or the like. Further, a list of policies created viaa “policies” section (see previous figures) may be shown and provisionedusing a two-window selection menu 1004.

FIG. 11 illustrates one possible graphical user interface 1100 forproviding details on applied policies, in accordance with oneembodiment. As an option, the present graphical user interface 1100 maybe implemented in the context of the architecture and environment ofFIGS. 1 and/or 2. Of course, however, the graphical user interface 1100may be carried out in any desired environment.

in one embodiment, an administrator of subscribers many need to login tothe present embodiment to see a pertinent configuration, view logs,create users who can log in, etc. The present graphical user interface1100 is what may be referred to as a “subscriber portal.” The presentgraphical user interface 1100 ensures that a customer logging in doesnot see upper domain information (if he/she is not permitted).

As shown in FIG. 11, an “applied policy detail” window 1101 is provided.In one embodiment, a user does not see any details on policies appliedabove his/her domain. For example, in FIG. 11, an end customer calledCustomer ABC is shown to be logged in. Note that the information“crossed-out” 1102 should not be shown since it relates to higher levelor parallel domain information. Further, the “Sensor” section has beenshown since this is how the user can “update” the sensor when he/shemakes changes (if they have permission to do that, of course). Hence, itis not crossed-out.

FIG. 12 illustrates one possible graphical user interface 1200 forproviding content/uniform resource locator (URL) filtering, inaccordance with one embodiment. As an option, the present graphical userinterface 1200 may be implemented in the context of the architecture andenvironment of FIGS. 1 and/or 2. Of course, however, the graphical userinterface 1200 may be carried out in any desired environment.

In one embodiment, the aforementioned filtering may include the abilityto block ActiveX components, Java applets, and/or scripting languages.In yet another embodiment, an ability may be provided for allowing auser to block a specific regular expression-based URL and, if possible,some body content. Further, a feature may be provided for includingpre-created profiles to block categories of content.

The foregoing functionality may be implemented on a “per user” basis ina domain, by linking to an authentication and user paradigm. As anoption, there may be exception lists with which one may specify a listof source anchor destination IPs/hostnames/domain names, etc.

As shown in FIG. 12, the graphical user interface 1200 may include ablock downloadable objects section 1202 and a block access to specificsites section 1204.

The block downloadable objects section 1202 is shown to include aplurality of selection icons 1206 for selecting to remove ActiveX,scripting, etc. from a page that is passed through. A user can furtheradd more items to block by configuring a regular expression, and evenblock files above a certain user-configured size, as shown. There isfurther an others input window 1208 (and associated add, edit, anddelete options) for providing exception lists. For items in such othersinput window 1208, there is no removal of links to the other object, butrather just blockage of the actual download of the object when there isa click on an associated link.

The block access to specific sites section 1204 similarly includesassociated add, edit, and delete options, and an associated table 1210for listing different site categories, to whom they apply, a time Whenthey apply, and a comment. There is also an input for allowing a user tochoose a web page to show when an access request is denied.

When a create new category option 1212 is selected, the graphical userinterface 1300 shown in FIG. 13 is displayed. As shown, the graphicaluser interface 1300 allows the user to configure regular expressions (inthe URL) that are to be blocked, it should be noted that a database maybe provided, so that the user may simply select a category whereby allthe websites that fall into such category would automatically be takenfrom the database and applied. This may save the user from having toenter in the numerous regular expressions.

As an option, access attempts may also be logged in a content filteringlog with a username (or IP, hostname, etc.) so that an administrator canuse a report generator to show the attempted accesses by a specificemployee of restricted web sites or content.

Further, each subscriber may be able to produce a log specific toactivities, etc. of the subscriber. For example, some customers of aservice provider may need to see specific firewall, virus scanner,intrusion prevention system (IPS), or content filtering logs. In oneembodiment, the format of the log may be a customizable log format.

Enforcinging, subscriber constraint requirements may be accomplished inany desired manner. Customers, in one embodiment, may be given numerouscontrols to ensure a few subscribers do not monopolize the presentsystem inappropriately. For example, the following parameters of Table 2may be optionally configured by each subscriber, or per any higher leveldomain (i.e. someone may want to enforce this on One interface group, oron one interface, etc).

TABLE 2 Maximum Number of ACL Entries Maximum Number of NAT/PAT EntriesMaximum Number of Routes Maximum Number of TCP flows at one time MaximumNumber of Content Filtering Rules Maximum Number of Sub-Admin Domainsthat can be created Maximum Number of SSL Keys What Type of Reports theyCan Generate, Maximum Number of Times they Can Schedule Reports, & HowMany They Can Schedule (and optionally even time constraints on whenthey can)

FIG. 14 illustrates a system 1400 for implementing service providermanagement hooks, in accordance with one embodiment. As an option, thepresent system 1400 may be implemented in the context of thearchitecture and environment of FIGS. 1 and/or 2. Of course, however,the system 1400 may be carried out in any desired environment.

Optionally, the security services may be managed by a standalonemanagement console or using another management interface or tool. Asshown in FIG. 14, a dual environment is set forth which may besupported.

Table 3 sets forth two management systems to which service providers mayneed to connect.

TABLE 3 Operations Support Systems (OSS)/Billing Support Systems (BSS):An OSS system may be used to support operational issues such as accountactivation, provisioning, service assurance, and usage/metering. A BSSsystem may be used for billing including invoicing, rating, taxation,collections, and customer management including order entry, customerself services, customer care, trouble ticketing, and customerrelationship management. Network Management Systems (NMS): These may beused for tracking performance, updating software, etc.

Thus, an interface may be provided which allows service providers tointegrate the present security services product into the foregoingsystems. Some additional optional features are set forth in Table 4.

TABLE 4 The interface may be able to issue commands and collectinformation at the domain level (i.e. one can set policies and provisionfor a whole domain or just one device, or just one VLAN of a device,etc. via a command. Each security function (i.e. HTTP virus scanner,firewall, IPS, HTTP content filtering, etc) may have a published set ofAPIs (if needed) for allowing one to add APIs as new functions are addedor if there is a need to revise (maintaining backward compatibility) theAPIs.

FIGS. 15-16 illustrate systems 1500-1600 for providing a failoverfeature. As an option, the present systems 1500-1600 may be implementedin the context of the architecture and environment of FIGS. 1 and/or 2.Of course, however, the systems 1500-1600 may be carried out in anydesired environment.

The mechanism for supporting a failover feature may be different inrouting mode and transparent mode. In the present embodiment, thefailover feature may allow a customer to minimize downtime due to sensormalfunction or upgrade by using a pair of sensors instead of one.Typically, in routing mode, one of the sensors may be active at anypoint of time while the other is in a standby mode ready to take overtraffic handling should the active sensor fail for any reason.

In transparent mode, both the sensors may be active and both the sensorsmay process traffic in an asymmetric way. In addition, the samefunctionality may be supported by using two cards in a single chassis.

In routing mode, one card or set of ports on one card may be active anda set of ports on another card may be in standby mode. To supportfailover, both sensors or both cards in a chassis may exchange stateinformation to ensure existing active flows on the failed system may beprocessed on the now active system. The following description may applyto routing mode operation.

FIG. 15 shows a pair of switches 1502 coupling a pair of parallelsecurity systems 1504 (an active security system 1504A and a standbysecurity system 1504B) between a router 1506 and a network 1508, in anactive/standby configuration.

The active and standby security systems 1504 provide alternate networkpaths for packets to flow between networks connected by the securitysystems 1504. When one security system 1504 fails, packets may be routedthrough the other security system 1504, and vice versa.

For high bandwidth scenarios, the system 1600 of FIG. 16 may be providedwith a “full mesh” configuration. As shown, a set of redundant switches1602 couple a pair of parallel security systems 1604 between virtualredundancy router protocol (VRRP) routers 1606 and a network 1608.

As shown, there are multiple redundant paths 1610. Traffic outage iscaused only when both the active and standby security systems 1604 of agiven type (i.e. switch, security system, router, etc.) fail. Thisconfiguration requires support for interface failover in addition todevice failover.

Each security system 1604 uses two interfaces (i.e. an active andstandby interface) for processing traffic from the network 1608. Onlyone of the two interfaces connected to the network 1608 is operationallyup (i.e. active) at any time. When the active interface goes down for aperiod of time, the backup interface is brought up to process traffic.When both interfaces connected to a network fail, traffic on thatinterface and related interfaces is switched over to the standbysecurity system, as described earlier.

In one example of use of the failover feature, two security systems arepaired as failover peers and enabled for failover. Such security systemsthen negotiate the active/standby status for each associated physicalport. At the end of this negotiation, one security system becomes theactive security system for all physical ports and the other becomes thestandby for all physical ports. Both the standby interfaces and theactive interfaces are always operationally up. The standby sensor may,however, drop all packets received on the standby ports.

At any time, traffic is received by the active security system whichperforms the necessary processing. Any packets received by the standbysecurity system on associated monitoring ports are dropped. The standbyand the active security systems exchange information to ensure that theassociated peer is still running. Such information includes anactive/standby status per port. If both security systems inform theother that it is active for a port, the security systems may renegotiatethe respective status, as set forth hereinabove.

The active security system continually monitors interface failure,hardware/software failure, and network failure on all interfaces. Whenany of the failures are detected, the active security system attempts toassume standby status for the failed ports (and related ports). Thestandby security system may not monitor failover conditions.

Traffic switchover from active to standby may be initiated either by thesecurity system or by an external device. At any time, the activesecurity system may request the standby security system to take over asthe active security system for any subset of interfaces. As an option,the standby security system may perform a set of tests to determine ifit is capable of taking over as the active security system. These testsmay be performed on a per-interface basis. Table 5 sets forth someexemplary tests.

TABLE 5 Network interface card (NIC) test: Check if the interface to bemade active is up. Address resolution protocol (ARP) test: Typically thesystem ARP cache is read for the 10 most recently acquired entries. ThenARP requests are sent to those machines to generate network traffic. Ifa non-zero number of packets are received on the interface within 5seconds, the interface is assumed to be operational. Ping test: Thesystem sends out a broadcast ping request and then counts all receivedpackets for 5 seconds. If any packets are received, the interface isconsidered good.

The following sequence of events of Table 6 may take place when activeto standby switchover is initiated, by the active security system for aparticular interface.

TABLE 6 1. The active security system determines that an interface hasfailed. 2. The active security system requests the standby securitysystem to assume the active role for the interface. 3. The standbysecurity system issues ARP requests to the set of configured IPaddresses on the interface. 4. The standby security system verifies ifit received a reply from each of the IP addresses within the configuredtimeout. If so, it communicates the information using the failoverprotocol. The active and the standby security system switch roles. 5.The standby (now active) security system issues gratuitous ARP requestsfor all IP addresses configured on the port. A gratuitous ARP occurswhen a host sends an ARP request looking for its own IP address. The ARPprotocol (RFC 826) requires that if a host receives an ARP request froman IP address that is already in the receiver cache, then such cacheentry is updated with the sender Ethernet address from the ARP request.The gratuitous ARPs therefore update the ARP caches of routers and hostsadjacent to the security system. Gratuitous ARPs are issued for allports by the active security system at initialization. 6. If the standbydetermines it is unfit for assuming the active role in Step 4, itinforms the active security system of this failure. The active securitysystem then issues gratuitous ARPs for all IP addresses configured onthe port. The active security system continues to be the active securitysystem for that port.

Traffic switched over by an external device can trigger a switch over bythe security system. Thus, if a router connected to the active securitysystem switched over the traffic to the standby security system, itsignals the active security system either by bringing down an interfaceor by not responding to the ARP requests. If a switchover happenedfarther than the immediate device connected to the security system, theactive security system may determine that the network path has failedand initiate switchover of the interface to the standby security system.

In one embodiment, terrorism may be countered utilizing theaforementioned technology. According to the U.S. Federal Bureau ofInvestigation, cyber-terrorism is any “premeditated, politicallymotivated attack against information, computer systems, computerprograms, and data which results in violence against non-combatanttargets by sub-national groups or clandestine agents.” A cyber-terroristattack is designed to cause physical violence or extreme financial harm.According to the U.S. Commission of Critical Infrastructure Protection,possible cyber-terrorist targets include the banking industry, militaryinstallations, power plants, air traffic control centers, and watersystems. Thus, by optionally incorporating the present technology intothe cyber-frameworks of the foregoing potential targets, terrorism maybe countered by preventing the infection thereof with malware, which maypotentially cause extreme financial harm.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. For example, any of the network elements may employ any ofthe desired functionality set forth hereinabove. Thus, the breadth andscope of a preferred embodiment should not be limited by any of theabove-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

1-18. (canceled)
 19. A security system, comprising: a pair of parallelsecurity systems that include virtual redundancy router protocol (VRRP)routers, wherein each VRRP router includes a security sub-system,wherein the security sub-system includes a plurality of virtualfirewalls, a plurality of virtual intrusion prevention systems (IPSs),and a plurality of virtual virus scanners, wherein each of the virtualfirewalls, IPSs, and virus scanners are assigned to at least one of aplurality of users and are configured in a user-specific manner; and aset of redundant switches coupled to the pair of parallel securitysystems.
 20. The system as recited in claim 19, wherein at least one ofthe pair of parallel security systems further comprises: an activeinterface for processing traffic received from a network; and a standbyinterface.
 21. The system as recited in claim 20, wherein at least oneof the security systems is an active security system and the othersecurity system is a standby security system, and wherein if at leastone of the interfaces fail, traffic is routed to the standby securitysystem.
 22. The system as recited in claim 20, wherein the activeinterface and the standby interface are active and process traffic in anasymmetric way.
 23. The system as recited in claim 20, wherein theactive interface and the standby interface exchange state information toensure existing active flows on a failed active interface may beprocessed on the standby interface.
 24. The system as recited in claim19, wherein at least one of the security systems is an active securitysystem and the other security system is a standby security system, andwherein the active security system and the standby security systemexchange state information to ensure existing active flows on a failedactive security system may be processed on the standby security system.25. The system as recited in claim 19, wherein at least one of thesecurity systems is an active security system and the other securitysystem is a standby security system, and wherein packets received by thestandby security system are dropped.
 26. A method, comprising: assigninga plurality of virtual firewalls, a plurality of virtual intrusionprevention systems (IPSs), and a plurality of virtual virus scanners ina security sub-system to at least one of a plurality of users, wherein apair of parallel security systems includes virtual redundancy routerprotocol (VRRP) routers, and each VRRP router includes the securitysub-system; configuring the plurality of virtual firewalls, theplurality of virtual intrusion prevention systems (IPSs), and theplurality of virtual virus scanners in a user-specific manner; andcoupling a set of redundant switches to the pair of parallel securitysystems.
 27. The method of claim 26, wherein at least one of the pair ofparallel security systems further comprises: an active interface forprocessing traffic received from a network; and a standby interface. 28.The method of claim 27, wherein at least one of the security systems isan active security system and the other security system is a standbysecurity system, and wherein if at least one of the interfaces fail,traffic is routed to the standby security system.
 29. The method ofclaim 27, wherein the active interface and the standby interface areactive and process traffic in an asymmetric way.
 30. The method of claim27, further comprising: exchanging state information between the activeinterface and the standby interface to ensure existing active flows on afailed active interface may be processed on the standby interface. 31.The method of claim 26, further comprising: wherein at least one of thesecurity systems is an active security system and the other securitysystem is a standby security system, and wherein the active securitysystem and the standby security system exchange state information toensure existing active flows on a failed active security system may beprocessed on the standby security system.
 32. The method of claim 26,wherein at least one of the security systems is an active securitysystem and the other security system is a standby security system, andwherein packets received by the standby security system are dropped. 33.Logic encoded in non-transitory media that includes code for executionand when executed by a processor operable to perform operationscomprising: assigning a plurality of virtual firewalls, a plurality ofvirtual intrusion prevention systems (IPSs), and a plurality of virtualvirus scanners in a security sub-system to at least one of a pluralityof users, wherein a pair of parallel security systems includes virtualredundancy router protocol (VRRP) routers, and each VRRP router includesthe security sub-system; configuring the plurality of virtual firewalls,the plurality of virtual intrusion prevention systems (IPSs), and theplurality of virtual virus scanners in a user-specific manner; andcoupling a set of redundant switches to the pair of parallel securitysystems.
 34. The logic of claim 33, wherein at least one of the pair ofparallel security systems further comprises: an active interface forprocessing traffic received from a network; and a standby interface. 35.The logic of claim 34, wherein at least one of the security systems isan active security system and the other security system is a standbysecurity system, and wherein if at least one of the interfaces fail,traffic is routed to the standby security system.
 36. The logic of claim34, wherein the active interface and the standby interface are activeand process traffic in an asymmetric way.
 37. The logic of claim 34,further comprising: exchanging state information between the activeinterface and the standby interface to ensure existing active flows on afailed active interface may be processed on the standby interface. 38.The logic of claim 33, wherein at least one of the security systems isan active security system and the other security system is a standbysecurity system, and wherein the active security system and the standbysecurity system exchange state information to ensure existing activeflows on a failed active security system may be processed on the standbysecurity system.